Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90e1550dc92144592972f2d36ceae2b745b70fefa96a8a7aa7d9c09f3b24f3bd

Tx prefix hash: dc7a8046a93c5c4a5eb8f24a2176c8fe62d6a638694248452e8dd4b417648810
Tx public key: 74eb9a89441a96f7c538320ebdabdee1a094751272b02ee834c1c7f672b12994
Timestamp: 1742989064 Timestamp [UCT]: 2025-03-26 11:37:44 Age [y:d:h:m:s]: 00:240:10:53:17
Block: 1247644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169608 RingCT/type: yes/0
Extra: 0174eb9a89441a96f7c538320ebdabdee1a094751272b02ee834c1c7f672b12994021100000002165b77a1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfe3c6842e27d9196aef2d6f0f4ca6c1b2113c21d593c511a2d76d5305f978ee 0.600000000000 1734671 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": 1247654, "vin": [ { "gen": { "height": 1247644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfe3c6842e27d9196aef2d6f0f4ca6c1b2113c21d593c511a2d76d5305f978ee" } } ], "extra": [ 1, 116, 235, 154, 137, 68, 26, 150, 247, 197, 56, 50, 14, 189, 171, 222, 225, 160, 148, 117, 18, 114, 176, 46, 232, 52, 193, 199, 246, 114, 177, 41, 148, 2, 17, 0, 0, 0, 2, 22, 91, 119, 161, 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