Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5762c102607b441e194d35c52d1ea901de262bf5a98be3b3e9e9898c7d7903a8

Tx prefix hash: edd94125ad62293a17454e50cf2fadfec8d5e5a75f62890ecb236482c5680d7e
Tx public key: 2fc2c00283891b8bc9ccb8bfe7818114213d5deac09f36d67dd6fe519304d944
Timestamp: 1577745050 Timestamp [UCT]: 2019-12-30 22:30:50 Age [y:d:h:m:s]: 05:062:14:20:29
Block: 35356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1194456 RingCT/type: yes/0
Extra: 012fc2c00283891b8bc9ccb8bfe7818114213d5deac09f36d67dd6fe519304d94402110000000e8a2ee0d9000000000000000000

1 output(s) for total of 468.653375567000 dcy

stealth address amount amount idx
00: 6414b7708d964b3c11b83469c7caa613cdedc5f1482294ca5fcf41a6ac33ed8c 468.653375567000 59572 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": 35366, "vin": [ { "gen": { "height": 35356 } } ], "vout": [ { "amount": 468653375567, "target": { "key": "6414b7708d964b3c11b83469c7caa613cdedc5f1482294ca5fcf41a6ac33ed8c" } } ], "extra": [ 1, 47, 194, 192, 2, 131, 137, 27, 139, 201, 204, 184, 191, 231, 129, 129, 20, 33, 61, 93, 234, 192, 159, 54, 214, 125, 214, 254, 81, 147, 4, 217, 68, 2, 17, 0, 0, 0, 14, 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