Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b45600cd42bce13949b9cefe349f115fdc75ed4d84ff1d069975f4906dd9dc7f

Tx prefix hash: f05101f2d40907f2d712439f02a38dd94d23fc8b87a0484a3efae53ecffd822f
Tx public key: 897910789d6341b0c91c2a68bc6d8aa082582ca91844f0607514f4e29b08a759
Timestamp: 1722130576 Timestamp [UCT]: 2024-07-28 01:36:16 Age [y:d:h:m:s]: 00:120:05:13:08
Block: 1075212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86015 RingCT/type: yes/0
Extra: 01897910789d6341b0c91c2a68bc6d8aa082582ca91844f0607514f4e29b08a75902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6884912a62a777c2e713b3265d4f4a88de9c1145bad6e8fcc4839f9a4e98883 0.600000000000 1547735 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": 1075222, "vin": [ { "gen": { "height": 1075212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6884912a62a777c2e713b3265d4f4a88de9c1145bad6e8fcc4839f9a4e98883" } } ], "extra": [ 1, 137, 121, 16, 120, 157, 99, 65, 176, 201, 28, 42, 104, 188, 109, 138, 160, 130, 88, 44, 169, 24, 68, 240, 96, 117, 20, 244, 226, 155, 8, 167, 89, 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