Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89c69e4178633120d6d7138b90364c9d96340e5561ae82be2dd910ad89180d5d

Tx prefix hash: 07e56887f83554ea15c8d8f87ef610b5a230b11ea7c1417e0e38ccb7c81e090d
Tx public key: d2739c0edead6fbc19fcd7a65a4915da71e9be4a907a657c2a22039300cc83e9
Timestamp: 1717702051 Timestamp [UCT]: 2024-06-06 19:27:31 Age [y:d:h:m:s]: 00:234:21:28:12
Block: 1038508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167856 RingCT/type: yes/0
Extra: 01d2739c0edead6fbc19fcd7a65a4915da71e9be4a907a657c2a22039300cc83e90211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46978154645b989245b45266a91f38cce7f7f2468ef3e613e5b4da8e7cbaa4ca 0.600000000000 1507069 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": 1038518, "vin": [ { "gen": { "height": 1038508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46978154645b989245b45266a91f38cce7f7f2468ef3e613e5b4da8e7cbaa4ca" } } ], "extra": [ 1, 210, 115, 156, 14, 222, 173, 111, 188, 25, 252, 215, 166, 90, 73, 21, 218, 113, 233, 190, 74, 144, 122, 101, 124, 42, 34, 3, 147, 0, 204, 131, 233, 2, 17, 0, 0, 0, 3, 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