Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb48618bd77cf128cf6240e1d766b4015eaec8f2a27c6d5a945158d183e86100

Tx prefix hash: 370c61283f85a3a59152ad158f2f69f23cedca58bf9afbed6c08d1e1d17de9da
Tx public key: 0c5a9d116405ef5194b03c32c035a6a3c2b816ae69d15ebf83e3dc32d63762b0
Timestamp: 1716163401 Timestamp [UCT]: 2024-05-20 00:03:21 Age [y:d:h:m:s]: 00:324:14:46:53
Block: 1025751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232018 RingCT/type: yes/0
Extra: 010c5a9d116405ef5194b03c32c035a6a3c2b816ae69d15ebf83e3dc32d63762b00211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a826ee42032e1bec84b62f821f3d7cca1158030727352f21bf72350fe7a135a 0.600000000000 1492456 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": 1025761, "vin": [ { "gen": { "height": 1025751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a826ee42032e1bec84b62f821f3d7cca1158030727352f21bf72350fe7a135a" } } ], "extra": [ 1, 12, 90, 157, 17, 100, 5, 239, 81, 148, 176, 60, 50, 192, 53, 166, 163, 194, 184, 22, 174, 105, 209, 94, 191, 131, 227, 220, 50, 214, 55, 98, 176, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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