Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2779988c166f9dedff5bb5958a10a36e13aaf69094395b95b408e4494a50c2f9

Tx prefix hash: a37d6f17d636ddcb62cf62266f63c31376c3850900d18c2cfe1bc28d42a3fc3b
Tx public key: 453910a188ae9b973fd053099dfd77f93e69940ec3097341c8f1c2151f0be9c6
Timestamp: 1581312251 Timestamp [UCT]: 2020-02-10 05:24:11 Age [y:d:h:m:s]: 05:113:19:03:26
Block: 61757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1234231 RingCT/type: yes/0
Extra: 01453910a188ae9b973fd053099dfd77f93e69940ec3097341c8f1c2151f0be9c60211000000048a2ee0d9000000000000000000

1 output(s) for total of 383.154771436000 dcy

stealth address amount amount idx
00: eba826524c7ed71cdc548a05915f6f98e943ef85a85e323216c317204889435c 383.154771436000 113888 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": 61767, "vin": [ { "gen": { "height": 61757 } } ], "vout": [ { "amount": 383154771436, "target": { "key": "eba826524c7ed71cdc548a05915f6f98e943ef85a85e323216c317204889435c" } } ], "extra": [ 1, 69, 57, 16, 161, 136, 174, 155, 151, 63, 208, 83, 9, 157, 253, 119, 249, 62, 105, 148, 14, 195, 9, 115, 65, 200, 241, 194, 21, 31, 11, 233, 198, 2, 17, 0, 0, 0, 4, 138, 46, 224, 217, 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