Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 6ac9fd0ff97af375653f64021d602b796ede3d262627a87e122150c102ead91f

Tx prefix hash: 4df07c1282b57f2da160f7b92ef9df4ef18ab94fd977d8fcd0791dc281c3d840
Tx public key: 9008036c2995b5aa749faa7990a8f40dcbf510f23d405d02cf0d811c2df47a6a
Timestamp: 1735703725 Timestamp [UCT]: 2025-01-01 03:55:25 Age [y:d:h:m:s]: 00:073:05:26:15
Block: 1187614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52133 RingCT/type: yes/0
Extra: 019008036c2995b5aa749faa7990a8f40dcbf510f23d405d02cf0d811c2df47a6a02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 307169fb5681662ca2dcd52a2c2ac5b08e5e389c47d454f1dd720bdaf1995bd5 0.600000000000 1674107 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1187624, "vin": [ { "gen": { "height": 1187614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "307169fb5681662ca2dcd52a2c2ac5b08e5e389c47d454f1dd720bdaf1995bd5" } } ], "extra": [ 1, 144, 8, 3, 108, 41, 149, 181, 170, 116, 159, 170, 121, 144, 168, 244, 13, 203, 245, 16, 242, 61, 64, 93, 2, 207, 13, 129, 28, 45, 244, 122, 106, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8