Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bb136d55a9c7b4662f9e6dad7a071a5acd78dc9fd046463e73c3141e5df6ef5

Tx prefix hash: 9683800f0d5286a9b5c160b8c718037ac4259b85c4c5cad7bd23c6baa866dbee
Tx public key: 4328380725e1dc19437dc8ba7ad71f2e25aff0c4b728841b5eb2bbb0d7aefcfa
Timestamp: 1711504278 Timestamp [UCT]: 2024-03-27 01:51:18 Age [y:d:h:m:s]: 01:006:02:28:45
Block: 987146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265292 RingCT/type: yes/0
Extra: 014328380725e1dc19437dc8ba7ad71f2e25aff0c4b728841b5eb2bbb0d7aefcfa0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9752625fb808bf8d6cb79e9fd4d47422c062505334205b6f27ebdd6aea7d08a3 0.600000000000 1447387 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": 987156, "vin": [ { "gen": { "height": 987146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9752625fb808bf8d6cb79e9fd4d47422c062505334205b6f27ebdd6aea7d08a3" } } ], "extra": [ 1, 67, 40, 56, 7, 37, 225, 220, 25, 67, 125, 200, 186, 122, 215, 31, 46, 37, 175, 240, 196, 183, 40, 132, 27, 94, 178, 187, 176, 215, 174, 252, 250, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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