Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ce2d2f55f44fe22699bd889832c8eddd38340129cf463b3b1cb5da10470c609

Tx prefix hash: 0932f974aa96dfd1d967c6b49586806c6d6fa19c69ebc8db69ebf5f8b91d3e3b
Tx public key: 511bf895ec36c62c3c5942f399c4a3b54b88794405c1340e94daecf16375a4ee
Timestamp: 1744436807 Timestamp [UCT]: 2025-04-12 05:46:47 Age [y:d:h:m:s]: 00:293:04:08:28
Block: 1259643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207178 RingCT/type: yes/0
Extra: 01511bf895ec36c62c3c5942f399c4a3b54b88794405c1340e94daecf16375a4ee0211000000026c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a9ffc60b0a795c9c182ba9445fd09acd2576c916bbb8ef026169b3e86910bdc 0.600000000000 1746792 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": 1259653, "vin": [ { "gen": { "height": 1259643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a9ffc60b0a795c9c182ba9445fd09acd2576c916bbb8ef026169b3e86910bdc" } } ], "extra": [ 1, 81, 27, 248, 149, 236, 54, 198, 44, 60, 89, 66, 243, 153, 196, 163, 181, 75, 136, 121, 68, 5, 193, 52, 14, 148, 218, 236, 241, 99, 117, 164, 238, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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