Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eda31d6b61f30f031c2bde57aa5d61812cbaad634aa679a621464b12f883f38c

Tx prefix hash: c954084aa268179b0ed8cb443860f09d1a8593af888474dc1737a9eb351224f7
Tx public key: 0fbd627d4299468bdf8b12711bce1a44fac60a912e24c055d8e01ca646c54230
Timestamp: 1712071764 Timestamp [UCT]: 2024-04-02 15:29:24 Age [y:d:h:m:s]: 01:023:13:12:40
Block: 991795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277828 RingCT/type: yes/0
Extra: 010fbd627d4299468bdf8b12711bce1a44fac60a912e24c055d8e01ca646c542300211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bd5a7eb870d66394cb3ec3065c89d5f8d8d2d92e391a6bf6d5a807b9568f5cf 0.600000000000 1452131 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": 991805, "vin": [ { "gen": { "height": 991795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bd5a7eb870d66394cb3ec3065c89d5f8d8d2d92e391a6bf6d5a807b9568f5cf" } } ], "extra": [ 1, 15, 189, 98, 125, 66, 153, 70, 139, 223, 139, 18, 113, 27, 206, 26, 68, 250, 198, 10, 145, 46, 36, 192, 85, 216, 224, 28, 166, 70, 197, 66, 48, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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