Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15ffbdbdee4213b36b690dc763991b554e15694dc84463c8af3136a512165664

Tx prefix hash: 28de95096e6576c3c4891396a80af02d2b8b17ccd69c0e08ce7b0a09c9636fbf
Tx public key: aedde1e09eb3d8f7e50d7b2f97682e70644b5a949099f0febe62fa4101a1b707
Timestamp: 1723849147 Timestamp [UCT]: 2024-08-16 22:59:07 Age [y:d:h:m:s]: 01:097:20:41:52
Block: 1089469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328412 RingCT/type: yes/0
Extra: 01aedde1e09eb3d8f7e50d7b2f97682e70644b5a949099f0febe62fa4101a1b70702110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72e77d9d36822deb4fa3907c0c9618c7fd52b5e9e8d7c98d1025b927e710ad54 0.600000000000 1564090 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": 1089479, "vin": [ { "gen": { "height": 1089469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72e77d9d36822deb4fa3907c0c9618c7fd52b5e9e8d7c98d1025b927e710ad54" } } ], "extra": [ 1, 174, 221, 225, 224, 158, 179, 216, 247, 229, 13, 123, 47, 151, 104, 46, 112, 100, 75, 90, 148, 144, 153, 240, 254, 190, 98, 250, 65, 1, 161, 183, 7, 2, 17, 0, 0, 0, 4, 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