Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca064fb8e1eb0f6f34d79a6086db26dccf2292507f5371b9fca8e6d282e84056

Tx prefix hash: 57804189b4cb26db3675277ca2284497c29aad6d64fe6628540eea1f466d50ef
Tx public key: 948ef31952a0f7207a0492fcafbbafb11f2818c0a6f5ec918809fd959bd9ff60
Timestamp: 1578433583 Timestamp [UCT]: 2020-01-07 21:46:23 Age [y:d:h:m:s]: 05:057:13:40:15
Block: 40790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1191128 RingCT/type: yes/0
Extra: 01948ef31952a0f7207a0492fcafbbafb11f2818c0a6f5ec918809fd959bd9ff6002110000000f49b77a3d000000000000000000

1 output(s) for total of 449.636588543000 dcy

stealth address amount amount idx
00: 5ebfa8129bc55403eaba55b0d3eba7ab74a5268a08e4027a3664522bf5f4e4a2 449.636588543000 71973 of 0

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": 40800, "vin": [ { "gen": { "height": 40790 } } ], "vout": [ { "amount": 449636588543, "target": { "key": "5ebfa8129bc55403eaba55b0d3eba7ab74a5268a08e4027a3664522bf5f4e4a2" } } ], "extra": [ 1, 148, 142, 243, 25, 82, 160, 247, 32, 122, 4, 146, 252, 175, 187, 175, 177, 31, 40, 24, 192, 166, 245, 236, 145, 136, 9, 253, 149, 155, 217, 255, 96, 2, 17, 0, 0, 0, 15, 73, 183, 122, 61, 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