Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfcb25597bce27f2680bdc4dcc1ca1694b4c1c772863dae1f5985825e5eb7552

Tx prefix hash: 274595d190a6ac8a393a31a55d2569234eacdc2d63adc19a7287a7cb9e2bf670
Tx public key: 62025c875bd7c7bc3843e36ad1c6e443bebcef37c9aad31c80da6772e707b84d
Timestamp: 1697168299 Timestamp [UCT]: 2023-10-13 03:38:19 Age [y:d:h:m:s]: 01:173:22:20:20
Block: 868467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385334 RingCT/type: yes/0
Extra: 0162025c875bd7c7bc3843e36ad1c6e443bebcef37c9aad31c80da6772e707b84d0211000000024b8f5122000000000000000000

1 output(s) for total of 0.813595131000 dcy

stealth address amount amount idx
00: 780db58e97a03c36a508a33eb0fb21f6e179b6e1e3217e1c17ee4a8945cb509e 0.813595131000 1323278 of 0

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": 868477, "vin": [ { "gen": { "height": 868467 } } ], "vout": [ { "amount": 813595131, "target": { "key": "780db58e97a03c36a508a33eb0fb21f6e179b6e1e3217e1c17ee4a8945cb509e" } } ], "extra": [ 1, 98, 2, 92, 135, 91, 215, 199, 188, 56, 67, 227, 106, 209, 198, 228, 67, 190, 188, 239, 55, 201, 170, 211, 28, 128, 218, 103, 114, 231, 7, 184, 77, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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