Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90c7f8035d2b61fd23d94581ea4206c36ae2a4ccd0fe9ef720df5ab43f19f1ba

Tx prefix hash: 1c79729abd8954e1ea2ff57a1a54a4176d09150010bc91821900a54d4baef704
Tx public key: 9404d7358fdbd49a1b6a72b2af9540cf13c3bb5ba1bfd06f4964010922be6cec
Timestamp: 1708996172 Timestamp [UCT]: 2024-02-27 01:09:32 Age [y:d:h:m:s]: 01:050:12:53:06
Block: 966334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297128 RingCT/type: yes/0
Extra: 019404d7358fdbd49a1b6a72b2af9540cf13c3bb5ba1bfd06f4964010922be6cec0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 029a5ea9e4bb559e6905973a28fef50e1e1ec2a2562ce53406785752645e84fc 0.600000000000 1426091 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": 966344, "vin": [ { "gen": { "height": 966334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "029a5ea9e4bb559e6905973a28fef50e1e1ec2a2562ce53406785752645e84fc" } } ], "extra": [ 1, 148, 4, 215, 53, 143, 219, 212, 154, 27, 106, 114, 178, 175, 149, 64, 207, 19, 195, 187, 91, 161, 191, 208, 111, 73, 100, 1, 9, 34, 190, 108, 236, 2, 17, 0, 0, 0, 1, 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