Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c533967bfdb83c7f67bcb2f60e024bcb2f45dfd4b265c172fd37651bbc54fa9

Tx prefix hash: b81ad50b4a0b6a4eb41400fc33f239a9f3d94f88fd5f67e2322a3cb6c7f079d9
Tx public key: 25f292d6324d691a469dfea840d3b39bfe0135030b2901db914416ab0c339acf
Timestamp: 1702664453 Timestamp [UCT]: 2023-12-15 18:20:53 Age [y:d:h:m:s]: 01:329:21:34:51
Block: 913830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494636 RingCT/type: yes/0
Extra: 0125f292d6324d691a469dfea840d3b39bfe0135030b2901db914416ab0c339acf02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1da61832b752c0adcb13ab6e8ba9d52b26236dba6b7ee50c16f0331c7b21b9f4 0.600000000000 1371110 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": 913840, "vin": [ { "gen": { "height": 913830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1da61832b752c0adcb13ab6e8ba9d52b26236dba6b7ee50c16f0331c7b21b9f4" } } ], "extra": [ 1, 37, 242, 146, 214, 50, 77, 105, 26, 70, 157, 254, 168, 64, 211, 179, 155, 254, 1, 53, 3, 11, 41, 1, 219, 145, 68, 22, 171, 12, 51, 154, 207, 2, 17, 0, 0, 0, 3, 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