Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9052991d9dbc528c0d5f10fbcbca330300897975031f87bb727c07bb590f596

Tx prefix hash: 1db37f3ac079730d3e797d3d1fdc2369da5c4b8efa7e1c35a4d9ed8f39462e28
Tx public key: d7a56f2bcbe592ae45795d8106ba48427ae34fc3d96645c859c6fad778b9ebcc
Timestamp: 1738433851 Timestamp [UCT]: 2025-02-01 18:17:31 Age [y:d:h:m:s]: 00:292:04:09:49
Block: 1209954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206576 RingCT/type: yes/0
Extra: 01d7a56f2bcbe592ae45795d8106ba48427ae34fc3d96645c859c6fad778b9ebcc0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ce267d1026552d835a06fb8ecf006cc6b52a352daa5f701ea72d8aef8f91d7a 0.600000000000 1696701 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": 1209964, "vin": [ { "gen": { "height": 1209954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ce267d1026552d835a06fb8ecf006cc6b52a352daa5f701ea72d8aef8f91d7a" } } ], "extra": [ 1, 215, 165, 111, 43, 203, 229, 146, 174, 69, 121, 93, 129, 6, 186, 72, 66, 122, 227, 79, 195, 217, 102, 69, 200, 89, 198, 250, 215, 120, 185, 235, 204, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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