Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83767451f695c0dd5a72511f19b3e6648141e9bd43f78760e8997dfb09e41921

Tx prefix hash: e21c957b75865754e78e5e5d2ee865efeeb0155302f8048f2047d6c0ce58a0d4
Tx public key: 3a0cf919e859f58653c95e57f9c60cbb2829e997801f6cc5822683d82ca0d828
Timestamp: 1723226717 Timestamp [UCT]: 2024-08-09 18:05:17 Age [y:d:h:m:s]: 00:236:06:24:20
Block: 1084308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168726 RingCT/type: yes/0
Extra: 013a0cf919e859f58653c95e57f9c60cbb2829e997801f6cc5822683d82ca0d82802110000001791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c56d09f0a5ee7fb87e14b3c319c5daf85c1ad50527599c1c371a189b6919a6b 0.600000000000 1558537 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": 1084318, "vin": [ { "gen": { "height": 1084308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c56d09f0a5ee7fb87e14b3c319c5daf85c1ad50527599c1c371a189b6919a6b" } } ], "extra": [ 1, 58, 12, 249, 25, 232, 89, 245, 134, 83, 201, 94, 87, 249, 198, 12, 187, 40, 41, 233, 151, 128, 31, 108, 197, 130, 38, 131, 216, 44, 160, 216, 40, 2, 17, 0, 0, 0, 23, 145, 225, 60, 4, 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