Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68cde242ce68bf79a9f6cfe7210eb978ec7a8aaa54c6bf0126245d7ce44f7733

Tx prefix hash: 0087c5b1166e90290547917ed8eb4485c9cfda482630cc3e2baff9f2c8a9681b
Tx public key: e4e92df8981c04aae89067736f390364a81217bf46e2c5f82b48821b6cea62c8
Timestamp: 1712305446 Timestamp [UCT]: 2024-04-05 08:24:06 Age [y:d:h:m:s]: 00:280:07:21:52
Block: 993733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200670 RingCT/type: yes/0
Extra: 01e4e92df8981c04aae89067736f390364a81217bf46e2c5f82b48821b6cea62c802110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85213d333da7509d7c70f3679a5a3e7f1a830d8d886d0423e456a36940fcc9c5 0.600000000000 1454121 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": 993743, "vin": [ { "gen": { "height": 993733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85213d333da7509d7c70f3679a5a3e7f1a830d8d886d0423e456a36940fcc9c5" } } ], "extra": [ 1, 228, 233, 45, 248, 152, 28, 4, 170, 232, 144, 103, 115, 111, 57, 3, 100, 168, 18, 23, 191, 70, 226, 197, 248, 43, 72, 130, 27, 108, 234, 98, 200, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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