Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cd1175ca146a179c2e6dcd85c255933a2fc0deb97141e90cc521baf6a55edc9

Tx prefix hash: 9136309a5f53a6b912825b5cc52e4e820590e751574638fbb6d041b8322bb04f
Tx public key: 3434dde43c11284dd81c6aa20b3ad2da03b2b0e2e08311f986bee5a8fe3ce9cb
Timestamp: 1720156455 Timestamp [UCT]: 2024-07-05 05:14:15 Age [y:d:h:m:s]: 00:340:20:02:28
Block: 1058847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243589 RingCT/type: yes/0
Extra: 013434dde43c11284dd81c6aa20b3ad2da03b2b0e2e08311f986bee5a8fe3ce9cb0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60f3417e7d50e41f94d64890954de57e203e49a56f16369afd48a1011f8b481c 0.600000000000 1529306 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": 1058857, "vin": [ { "gen": { "height": 1058847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60f3417e7d50e41f94d64890954de57e203e49a56f16369afd48a1011f8b481c" } } ], "extra": [ 1, 52, 52, 221, 228, 60, 17, 40, 77, 216, 28, 106, 162, 11, 58, 210, 218, 3, 178, 176, 226, 224, 131, 17, 249, 134, 190, 229, 168, 254, 60, 233, 203, 2, 17, 0, 0, 0, 6, 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