Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5639d8ba05bf582a3c1de0923de712564cef238db880c936ec8e31b5be4a8cf1

Tx prefix hash: e4711bbe973ca579f187d3767cd4fb632f10370f5a19f857e0fb648ba22e5969
Tx public key: 50bd4cb7051aae45450b5cee92e8ca96996844aa0c25f7dea4b8315bdc90d1c6
Timestamp: 1729539571 Timestamp [UCT]: 2024-10-21 19:39:31 Age [y:d:h:m:s]: 00:185:12:19:49
Block: 1136606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132409 RingCT/type: yes/0
Extra: 0150bd4cb7051aae45450b5cee92e8ca96996844aa0c25f7dea4b8315bdc90d1c6021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3361e4c5a29d58f3ede282acb13c2fce2481deaf013cafe0258246fb4767c0db 0.600000000000 1619953 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": 1136616, "vin": [ { "gen": { "height": 1136606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3361e4c5a29d58f3ede282acb13c2fce2481deaf013cafe0258246fb4767c0db" } } ], "extra": [ 1, 80, 189, 76, 183, 5, 26, 174, 69, 69, 11, 92, 238, 146, 232, 202, 150, 153, 104, 68, 170, 12, 37, 247, 222, 164, 184, 49, 91, 220, 144, 209, 198, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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