Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbe2a708054b5ac5d98e42a891216a3bb52b30fa91062b5a5411661c0fd57336

Tx prefix hash: f53d6a9ce609f5416dde258571d6e83509a9428581641a4673468e6c7879f625
Tx public key: 90c6db332599c01de58a67ca30c20b0feeae59371bb2e754631b839c9da1df1b
Timestamp: 1751150363 Timestamp [UCT]: 2025-06-28 22:39:23 Age [y:d:h:m:s]: 00:133:23:25:52
Block: 1314809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93848 RingCT/type: yes/0
Extra: 0190c6db332599c01de58a67ca30c20b0feeae59371bb2e754631b839c9da1df1b021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1a28453f2292048491217b45a42f3b4b1aece04def9b1f770065d7dfad2b95a 0.600000000000 1802460 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": 1314819, "vin": [ { "gen": { "height": 1314809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1a28453f2292048491217b45a42f3b4b1aece04def9b1f770065d7dfad2b95a" } } ], "extra": [ 1, 144, 198, 219, 51, 37, 153, 192, 29, 229, 138, 103, 202, 48, 194, 11, 15, 238, 174, 89, 55, 27, 178, 231, 84, 99, 27, 131, 156, 157, 161, 223, 27, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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