Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3aa57db8ee3ff2fe2771b36f3284a66c02566cd8c794234705cd0aa3cf4a971

Tx prefix hash: 74c1c1e54ea9cbed563367f08a4e32c2a00a6649c944a22dccc11836c029f324
Tx public key: 3864c15f961d4b339cc94a3e4df88cdca06ffbf202e4ec9d52824a8455066bad
Timestamp: 1738474529 Timestamp [UCT]: 2025-02-02 05:35:29 Age [y:d:h:m:s]: 00:361:12:57:26
Block: 1210285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256077 RingCT/type: yes/0
Extra: 013864c15f961d4b339cc94a3e4df88cdca06ffbf202e4ec9d52824a8455066bad0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78cc276f6dc3b03a1718d3a28090cf6abc780f1a0b9ffc08de3eea29e5a253e8 0.600000000000 1697036 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": 1210295, "vin": [ { "gen": { "height": 1210285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78cc276f6dc3b03a1718d3a28090cf6abc780f1a0b9ffc08de3eea29e5a253e8" } } ], "extra": [ 1, 56, 100, 193, 95, 150, 29, 75, 51, 156, 201, 74, 62, 77, 248, 140, 220, 160, 111, 251, 242, 2, 228, 236, 157, 82, 130, 74, 132, 85, 6, 107, 173, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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