Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ef0e5d16010ba73b29f105283a17c92fe37080cc10e1b906aa1d9075834d86f

Tx prefix hash: 7752aef8e93fc374d61308449fc0b67aee436bcfa5c3f875aeab7aee1044d949
Tx public key: f5e7191552a78a506b4b3fb355067be7a5dca970d73cba631c423fdd8504c426
Timestamp: 1706916131 Timestamp [UCT]: 2024-02-02 23:22:11 Age [y:d:h:m:s]: 01:059:08:43:58
Block: 949065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303489 RingCT/type: yes/0
Extra: 01f5e7191552a78a506b4b3fb355067be7a5dca970d73cba631c423fdd8504c42602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcccdb3b4eed7fb13604570e900a02c8e6e561f6b99bc7b90142ded920adc908 0.600000000000 1407587 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": 949075, "vin": [ { "gen": { "height": 949065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcccdb3b4eed7fb13604570e900a02c8e6e561f6b99bc7b90142ded920adc908" } } ], "extra": [ 1, 245, 231, 25, 21, 82, 167, 138, 80, 107, 75, 63, 179, 85, 6, 123, 231, 165, 220, 169, 112, 215, 60, 186, 99, 28, 66, 63, 221, 133, 4, 196, 38, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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