Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6e23f67fcea08d91cdddb50aa02050c625bc44de8ca7bc8ffd3fa6412e14120

Tx prefix hash: b137cbf983f52d8f2e2e21975b515c4ace3e4820c79c6bc46cc22fbfca7b63bf
Tx public key: 345d9b741746b450d8e0a885a49eab769fe9559db2f788b63481475bae23c3f3
Timestamp: 1676916519 Timestamp [UCT]: 2023-02-20 18:08:39 Age [y:d:h:m:s]: 02:046:20:40:14
Block: 701250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 555087 RingCT/type: yes/0
Extra: 01345d9b741746b450d8e0a885a49eab769fe9559db2f788b63481475bae23c3f302110000000474b6d784000000000000000000

1 output(s) for total of 2.913852465000 dcy

stealth address amount amount idx
00: 5e35c248e79e3c61dd3ab7b36ab28ab6ff44ec3842f17aeade5ca5dab2e742b7 2.913852465000 1144721 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": 701260, "vin": [ { "gen": { "height": 701250 } } ], "vout": [ { "amount": 2913852465, "target": { "key": "5e35c248e79e3c61dd3ab7b36ab28ab6ff44ec3842f17aeade5ca5dab2e742b7" } } ], "extra": [ 1, 52, 93, 155, 116, 23, 70, 180, 80, 216, 224, 168, 133, 164, 158, 171, 118, 159, 233, 85, 157, 178, 247, 136, 182, 52, 129, 71, 91, 174, 35, 195, 243, 2, 17, 0, 0, 0, 4, 116, 182, 215, 132, 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