Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a920bbd5501c98419c4037bb14fc17fc9c18cf26e52a38c3186327f0448326da

Tx prefix hash: 7ba43c06f4db131a3b1f06542b37d5e739837c28f717455c771e80e7b8337dbe
Tx public key: cf1d4a031db1ed9d270e02aec245089a73c5cc5d2b563b6f3d10fd788cdcd933
Timestamp: 1704276389 Timestamp [UCT]: 2024-01-03 10:06:29 Age [y:d:h:m:s]: 01:105:14:43:38
Block: 927199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336580 RingCT/type: yes/0
Extra: 01cf1d4a031db1ed9d270e02aec245089a73c5cc5d2b563b6f3d10fd788cdcd93302110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6af1957f700041575591e774df8e3d5e8d172f34b1c047670b7ad2327abed2e 0.600000000000 1385005 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": 927209, "vin": [ { "gen": { "height": 927199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6af1957f700041575591e774df8e3d5e8d172f34b1c047670b7ad2327abed2e" } } ], "extra": [ 1, 207, 29, 74, 3, 29, 177, 237, 157, 39, 14, 2, 174, 194, 69, 8, 154, 115, 197, 204, 93, 43, 86, 59, 111, 61, 16, 253, 120, 140, 220, 217, 51, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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