Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbf4d737a1ea02fb75003a4e4f90263508e8f6cf2e8e5b721e3fc46d7971a8e7

Tx prefix hash: 19fd991ee6ee2f72404194cf9538f1c985454216bf60236f50fdb53fcdb7d68c
Tx public key: 030458b1f570ffdcc2816c15693b80982b5e5515aca1131ecac1108395bafe07
Timestamp: 1734869688 Timestamp [UCT]: 2024-12-22 12:14:48 Age [y:d:h:m:s]: 00:104:10:57:38
Block: 1180740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74418 RingCT/type: yes/0
Extra: 01030458b1f570ffdcc2816c15693b80982b5e5515aca1131ecac1108395bafe070211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bfdf9fc5aaa95924745a7b5d580bba891c2b21dd98d2c15ac70f0b6e0007f3a 0.600000000000 1667153 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": 1180750, "vin": [ { "gen": { "height": 1180740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bfdf9fc5aaa95924745a7b5d580bba891c2b21dd98d2c15ac70f0b6e0007f3a" } } ], "extra": [ 1, 3, 4, 88, 177, 245, 112, 255, 220, 194, 129, 108, 21, 105, 59, 128, 152, 43, 94, 85, 21, 172, 161, 19, 30, 202, 193, 16, 131, 149, 186, 254, 7, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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