Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2ee69aa22e83cb85db38c8e1029b2bd4322106011d87174b3a053e70639f03b

Tx prefix hash: 2cae154a35c5ff6ecf64f93c83ff35b6b9b300bcd93c10d1c63766faee9fef20
Tx public key: e7b588fce5c57fb815970c845eba87b95349206f1955d06e1af1c2651ea1091f
Timestamp: 1723809364 Timestamp [UCT]: 2024-08-16 11:56:04 Age [y:d:h:m:s]: 01:105:00:30:48
Block: 1089137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333553 RingCT/type: yes/0
Extra: 01e7b588fce5c57fb815970c845eba87b95349206f1955d06e1af1c2651ea1091f02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c58cacc3572c699f85aaba6c674aa82eeee7c3f7e434a8b9b08063c9354b4f48 0.600000000000 1563756 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": 1089147, "vin": [ { "gen": { "height": 1089137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c58cacc3572c699f85aaba6c674aa82eeee7c3f7e434a8b9b08063c9354b4f48" } } ], "extra": [ 1, 231, 181, 136, 252, 229, 197, 127, 184, 21, 151, 12, 132, 94, 186, 135, 185, 83, 73, 32, 111, 25, 85, 208, 110, 26, 241, 194, 101, 30, 161, 9, 31, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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