Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5b0db8299914d1337001c14587d2cbacf35c7b9d7061ca5ab711a49fb5a45d2

Tx prefix hash: 2664da2eb74bc5776b7a8ce74aa9c111f5f1f453f0f986df5669056352be9112
Tx public key: 72d12315e149f8b92a7e21d65556ae020174a558258f5ed04d8b4e0c445f3623
Timestamp: 1737536592 Timestamp [UCT]: 2025-01-22 09:03:12 Age [y:d:h:m:s]: 00:051:03:32:52
Block: 1202744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36388 RingCT/type: yes/0
Extra: 0172d12315e149f8b92a7e21d65556ae020174a558258f5ed04d8b4e0c445f36230211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ee018f7d89a90b8c950df6e154a73aa062c6c5fbf221725ba0efa3899c04655 0.600000000000 1689409 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": 1202754, "vin": [ { "gen": { "height": 1202744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ee018f7d89a90b8c950df6e154a73aa062c6c5fbf221725ba0efa3899c04655" } } ], "extra": [ 1, 114, 209, 35, 21, 225, 73, 248, 185, 42, 126, 33, 214, 85, 86, 174, 2, 1, 116, 165, 88, 37, 143, 94, 208, 77, 139, 78, 12, 68, 95, 54, 35, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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