Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44f0468b9cdf18ab1881b7779c821a5e41bd9fd8d578f81fd1117469728d42bd

Tx prefix hash: ff974694fd5a75288eaa8fefd71b955b71bdf7d0edee8285373084676a0639b2
Tx public key: 443cef45ce0b95130ce85c567b532d9fe1b759f36ff85eab06c43ad70aae0b89
Timestamp: 1682338718 Timestamp [UCT]: 2023-04-24 12:18:38 Age [y:d:h:m:s]: 01:263:05:32:43
Block: 745574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449608 RingCT/type: yes/0
Extra: 01443cef45ce0b95130ce85c567b532d9fe1b759f36ff85eab06c43ad70aae0b8902110000000475e3f0e9000000000000000000

1 output(s) for total of 2.077801451000 dcy

stealth address amount amount idx
00: 37f6a79a41a017afce611065986200541adb071083f2a5d54f6d8ad9d7bd2c59 2.077801451000 1193037 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": 745584, "vin": [ { "gen": { "height": 745574 } } ], "vout": [ { "amount": 2077801451, "target": { "key": "37f6a79a41a017afce611065986200541adb071083f2a5d54f6d8ad9d7bd2c59" } } ], "extra": [ 1, 68, 60, 239, 69, 206, 11, 149, 19, 12, 232, 92, 86, 123, 83, 45, 159, 225, 183, 89, 243, 111, 248, 94, 171, 6, 196, 58, 215, 10, 174, 11, 137, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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