Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11840bb371c8715aba26c8d476975c02c454a3e42fefed9ff83ef289d978b1d1

Tx prefix hash: 9c518e765ebd28f6a00f45d86e261b5abb7863b3b4e666a21e282d1248c9e9b1
Tx public key: 40a584bbbb1b6141de387fa5c6a3faee8e329acb7bec473ff7393542a16595d1
Timestamp: 1659585831 Timestamp [UCT]: 2022-08-04 04:03:51 Age [y:d:h:m:s]: 02:242:06:45:48
Block: 558279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 694368 RingCT/type: yes/0
Extra: 0140a584bbbb1b6141de387fa5c6a3faee8e329acb7bec473ff7393542a16595d10211000000056570b1ef000000000000000000

1 output(s) for total of 8.673413278000 dcy

stealth address amount amount idx
00: 5b764898f1adc88c38edfe8344df3f1d68f8bfa4808e600d7ac2b3a61f8f5135 8.673413278000 990347 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": 558289, "vin": [ { "gen": { "height": 558279 } } ], "vout": [ { "amount": 8673413278, "target": { "key": "5b764898f1adc88c38edfe8344df3f1d68f8bfa4808e600d7ac2b3a61f8f5135" } } ], "extra": [ 1, 64, 165, 132, 187, 187, 27, 97, 65, 222, 56, 127, 165, 198, 163, 250, 238, 142, 50, 154, 203, 123, 236, 71, 63, 247, 57, 53, 66, 161, 101, 149, 209, 2, 17, 0, 0, 0, 5, 101, 112, 177, 239, 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