Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0812ed703662425d833fa935b6ec3168a098877e785d101cfe6985a4bfc4cd63

Tx prefix hash: be98378e71310e5f21f2def391f6da6c4b1c36012aaeff39ee4906f93953f033
Tx public key: bfd0e601963337891a037af5c55f36de6c41c79b52a1a806ac795a6b1eed89f0
Timestamp: 1737733650 Timestamp [UCT]: 2025-01-24 15:47:30 Age [y:d:h:m:s]: 00:146:04:59:27
Block: 1204373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104222 RingCT/type: yes/0
Extra: 01bfd0e601963337891a037af5c55f36de6c41c79b52a1a806ac795a6b1eed89f00211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97c5c30a10a08608b6f6009c28f774d51a2db5f432e6bcd919a6d1df523a93a5 0.600000000000 1691058 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": 1204383, "vin": [ { "gen": { "height": 1204373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97c5c30a10a08608b6f6009c28f774d51a2db5f432e6bcd919a6d1df523a93a5" } } ], "extra": [ 1, 191, 208, 230, 1, 150, 51, 55, 137, 26, 3, 122, 245, 197, 95, 54, 222, 108, 65, 199, 155, 82, 161, 168, 6, 172, 121, 90, 107, 30, 237, 137, 240, 2, 17, 0, 0, 0, 6, 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