Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d87b7d9dc83bf5f7da04c5ed8e4e4c58518b951d1ddcd1fb882d83c4879bcd40

Tx prefix hash: ace1aa3ee4c81da197ddd0e5ac5398a1a228316a2d54fffbb15955eede8441cb
Tx public key: e1d29d4bacb34a6fb517a43cda5aa8412ed14bf2c5b19fcd8a80fa92f055fdb7
Timestamp: 1709490551 Timestamp [UCT]: 2024-03-03 18:29:11 Age [y:d:h:m:s]: 01:041:22:56:39
Block: 970435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290991 RingCT/type: yes/0
Extra: 01e1d29d4bacb34a6fb517a43cda5aa8412ed14bf2c5b19fcd8a80fa92f055fdb70211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: defbf30d0b4ebed31ef31bc55c0bf8a746610278d0d2edece9fe22f44f9747eb 0.600000000000 1430288 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": 970445, "vin": [ { "gen": { "height": 970435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "defbf30d0b4ebed31ef31bc55c0bf8a746610278d0d2edece9fe22f44f9747eb" } } ], "extra": [ 1, 225, 210, 157, 75, 172, 179, 74, 111, 181, 23, 164, 60, 218, 90, 168, 65, 46, 209, 75, 242, 197, 177, 159, 205, 138, 128, 250, 146, 240, 85, 253, 183, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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