Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 459c92d537f2049a711d46e20c44fd2e96d94a8b816dc372980c97e31e5de436

Tx prefix hash: 2c1f90ee15a44c5907d7981d485f673b79e474b4f846daf43614093ae9578671
Tx public key: 9e68184e502e044dce7b2f2f36faf228681f2beb5ec85537a7b610e1512c8ec0
Timestamp: 1636690624 Timestamp [UCT]: 2021-11-12 04:17:04 Age [y:d:h:m:s]: 02:361:14:23:54
Block: 372564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 776146 RingCT/type: yes/0
Extra: 019e68184e502e044dce7b2f2f36faf228681f2beb5ec85537a7b610e1512c8ec002110000004cf56b629f000000000000000000

1 output(s) for total of 35.771833434000 dcy

stealth address amount amount idx
00: bce3c03cf1d5dbb0c0645c302f023b1215f48bc0a0821159239dece0f03cd7ef 35.771833434000 754678 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": 372574, "vin": [ { "gen": { "height": 372564 } } ], "vout": [ { "amount": 35771833434, "target": { "key": "bce3c03cf1d5dbb0c0645c302f023b1215f48bc0a0821159239dece0f03cd7ef" } } ], "extra": [ 1, 158, 104, 24, 78, 80, 46, 4, 77, 206, 123, 47, 47, 54, 250, 242, 40, 104, 31, 43, 235, 94, 200, 85, 55, 167, 182, 16, 225, 81, 44, 142, 192, 2, 17, 0, 0, 0, 76, 245, 107, 98, 159, 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