Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b8cfec00d2d4fe4591742cfdf34c10cb0d5cb55ebb732322272a26f4f22c86b

Tx prefix hash: 78562bb5326b6fdd77c4ac511eec82721b180443ecf27889d55e520c3ec47cb1
Tx public key: f27b019acf8b1bd1a4f77298541dac7e6ef0d091c3fc01a650a27726f405b6ca
Timestamp: 1723812765 Timestamp [UCT]: 2024-08-16 12:52:45 Age [y:d:h:m:s]: 00:223:17:44:12
Block: 1089171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159768 RingCT/type: yes/0
Extra: 01f27b019acf8b1bd1a4f77298541dac7e6ef0d091c3fc01a650a27726f405b6ca02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87018982bbb07cb201eefcfc49b41cefb626fac702f8e96da9691864a88f5eda 0.600000000000 1563790 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": 1089181, "vin": [ { "gen": { "height": 1089171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87018982bbb07cb201eefcfc49b41cefb626fac702f8e96da9691864a88f5eda" } } ], "extra": [ 1, 242, 123, 1, 154, 207, 139, 27, 209, 164, 247, 114, 152, 84, 29, 172, 126, 110, 240, 208, 145, 195, 252, 1, 166, 80, 162, 119, 38, 244, 5, 182, 202, 2, 17, 0, 0, 0, 3, 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