Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fd2a30b37f5a0d4eaccbc818b5133a065c48055dc7319616201add680c8c56a

Tx prefix hash: e06c4422d93475ad15fea87730d0313dd9dc2433e35995e3a89f825ba7cbe1e3
Tx public key: ae42e4a00a503133a943bb98df5e0e935fe92c1d83a471fc8f55aeb91d23bb39
Timestamp: 1730241117 Timestamp [UCT]: 2024-10-29 22:31:57 Age [y:d:h:m:s]: 00:160:19:58:02
Block: 1142393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114765 RingCT/type: yes/0
Extra: 01ae42e4a00a503133a943bb98df5e0e935fe92c1d83a471fc8f55aeb91d23bb390211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1e2fc3fdb778cbd5a22bd7811726d590d79528e00b509c17aa8b8b3d2eb3eaa 0.600000000000 1626246 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": 1142403, "vin": [ { "gen": { "height": 1142393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1e2fc3fdb778cbd5a22bd7811726d590d79528e00b509c17aa8b8b3d2eb3eaa" } } ], "extra": [ 1, 174, 66, 228, 160, 10, 80, 49, 51, 169, 67, 187, 152, 223, 94, 14, 147, 95, 233, 44, 29, 131, 164, 113, 252, 143, 85, 174, 185, 29, 35, 187, 57, 2, 17, 0, 0, 0, 1, 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