Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9c3f20891dece1b95c8dde7a5837cb41d2cef81d76ebd928025df929fd7abf5

Tx prefix hash: 116d8f145779aed3d7dd9e6bc3231d0dcaf1042f49c97af6eb042fc3a668553f
Tx public key: bf99800ac1465668a4d5f99849e291fa3b81c58ea72db08b4241305af58ba1b8
Timestamp: 1723255210 Timestamp [UCT]: 2024-08-10 02:00:10 Age [y:d:h:m:s]: 00:256:07:49:32
Block: 1084544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183086 RingCT/type: yes/0
Extra: 01bf99800ac1465668a4d5f99849e291fa3b81c58ea72db08b4241305af58ba1b802110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dcbd869bbf8e2de8d29e9b46410acd1450e5e1e1161af851c98cfa6e59cea65 0.600000000000 1558857 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": 1084554, "vin": [ { "gen": { "height": 1084544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dcbd869bbf8e2de8d29e9b46410acd1450e5e1e1161af851c98cfa6e59cea65" } } ], "extra": [ 1, 191, 153, 128, 10, 193, 70, 86, 104, 164, 213, 249, 152, 73, 226, 145, 250, 59, 129, 197, 142, 167, 45, 176, 139, 66, 65, 48, 90, 245, 139, 161, 184, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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