Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42462851a0bac1116df5505f7ec5a215b4e283c2dd78976f35bf5afdc42c4010

Tx prefix hash: 3b83cc116f4143bbc6bb1cf08e4599b7af94e8d8350e8e15aca87fc93e7be2c6
Tx public key: fb3a1bf777cd1f1934953d657672e78f9355af2877b9e4430d46f938becc9842
Timestamp: 1701589674 Timestamp [UCT]: 2023-12-03 07:47:54 Age [y:d:h:m:s]: 01:136:22:16:18
Block: 904924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359027 RingCT/type: yes/0
Extra: 01fb3a1bf777cd1f1934953d657672e78f9355af2877b9e4430d46f938becc984202110000000575e3f0e9000000000000000000

1 output(s) for total of 0.616043121000 dcy

stealth address amount amount idx
00: 02e35085ebf87d272497e24c3df3fef72bdf61d3c17885a4959a2bece5a726c4 0.616043121000 1361709 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": 904934, "vin": [ { "gen": { "height": 904924 } } ], "vout": [ { "amount": 616043121, "target": { "key": "02e35085ebf87d272497e24c3df3fef72bdf61d3c17885a4959a2bece5a726c4" } } ], "extra": [ 1, 251, 58, 27, 247, 119, 205, 31, 25, 52, 149, 61, 101, 118, 114, 231, 143, 147, 85, 175, 40, 119, 185, 228, 67, 13, 70, 249, 56, 190, 204, 152, 66, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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