Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cdf0fb9ccaf8ce4478fc45c9bcf95cf283f269128e7e06b2e60f1669d00c5fc

Tx prefix hash: b6013e41d665612549d4f639115909b3717f3e95708e9474a446b8fba639c57d
Tx public key: 884d3d113e7a32e2b2d7b0aa89ae449672f8e64dd5de1b03fee68f6b82c440f7
Timestamp: 1577877726 Timestamp [UCT]: 2020-01-01 11:22:06 Age [y:d:h:m:s]: 05:099:22:06:40
Block: 36301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1221310 RingCT/type: yes/0
Extra: 01884d3d113e7a32e2b2d7b0aa89ae449672f8e64dd5de1b03fee68f6b82c440f70211000000288a2ee0d9000000000000000000

1 output(s) for total of 465.286627343000 dcy

stealth address amount amount idx
00: ab7a54037aa595a2c3ce7c00143e46e3149ae17f486fa09f9b7951ad5cf7c1a9 465.286627343000 61460 of 0

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": 36311, "vin": [ { "gen": { "height": 36301 } } ], "vout": [ { "amount": 465286627343, "target": { "key": "ab7a54037aa595a2c3ce7c00143e46e3149ae17f486fa09f9b7951ad5cf7c1a9" } } ], "extra": [ 1, 136, 77, 61, 17, 62, 122, 50, 226, 178, 215, 176, 170, 137, 174, 68, 150, 114, 248, 230, 77, 213, 222, 27, 3, 254, 230, 143, 107, 130, 196, 64, 247, 2, 17, 0, 0, 0, 40, 138, 46, 224, 217, 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