Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17c0dc1e6f729ac6eb21cf484653787f8a50b4a133b8767f914ca4c270e9fa1c

Tx prefix hash: 0399156adc602d0c7e722ddbf792b076eb2b4935ae470bd377d503bf4f9848e7
Tx public key: 9f3b8d3db48292d3127c49aa72ee717d16bbc9bd1caed43ee65d8a6ac5d188fe
Timestamp: 1577764002 Timestamp [UCT]: 2019-12-31 03:46:42 Age [y:d:h:m:s]: 05:104:17:17:08
Block: 35450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1224646 RingCT/type: yes/0
Extra: 019f3b8d3db48292d3127c49aa72ee717d16bbc9bd1caed43ee65d8a6ac5d188fe02110000000f4ac5aa02000000000000000000

1 output(s) for total of 468.317393875000 dcy

stealth address amount amount idx
00: a23cc2b40dcacb5ed7f57a4213f0a329c4882f28a4d1e334ac46ee8969a3a83d 468.317393875000 59799 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": 35460, "vin": [ { "gen": { "height": 35450 } } ], "vout": [ { "amount": 468317393875, "target": { "key": "a23cc2b40dcacb5ed7f57a4213f0a329c4882f28a4d1e334ac46ee8969a3a83d" } } ], "extra": [ 1, 159, 59, 141, 61, 180, 130, 146, 211, 18, 124, 73, 170, 114, 238, 113, 125, 22, 187, 201, 189, 28, 174, 212, 62, 230, 93, 138, 106, 197, 209, 136, 254, 2, 17, 0, 0, 0, 15, 74, 197, 170, 2, 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