Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a89e54fc30995eca1cc9a14a576cdaa545d68815c5509c7b52bef5da2f8b6e1b

Tx prefix hash: 062a217550a69edd157b538834424a51698aaa4da42f34b0718f972ad2378f9c
Tx public key: c861227618454bf8180a5cda2ed1c692991a848af35e2b0f5d6d9663fe82b081
Timestamp: 1717891056 Timestamp [UCT]: 2024-06-08 23:57:36 Age [y:d:h:m:s]: 00:176:11:35:45
Block: 1040075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126306 RingCT/type: yes/0
Extra: 01c861227618454bf8180a5cda2ed1c692991a848af35e2b0f5d6d9663fe82b0810211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbea3c35eac6f25b4af150652d81ccc9b2771c1d69f3e4d62a63bf3af9b7257b 0.600000000000 1508730 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": 1040085, "vin": [ { "gen": { "height": 1040075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbea3c35eac6f25b4af150652d81ccc9b2771c1d69f3e4d62a63bf3af9b7257b" } } ], "extra": [ 1, 200, 97, 34, 118, 24, 69, 75, 248, 24, 10, 92, 218, 46, 209, 198, 146, 153, 26, 132, 138, 243, 94, 43, 15, 93, 109, 150, 99, 254, 130, 176, 129, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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