Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef20fe02b357e5da65ac6464fdbf9ad6bbd8cc617bfdd2a674974b666fd6d352

Tx prefix hash: 7ecc6d0a2554244ccbeffd52a1cc5784a6135f912eeca303f050b1b1c68c45c1
Tx public key: d079bdc1079efc0ce411013f23f9c3a8c21af28756d5a78694237b7ef27e2b51
Timestamp: 1726074824 Timestamp [UCT]: 2024-09-11 17:13:44 Age [y:d:h:m:s]: 00:041:11:09:02
Block: 1107913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29675 RingCT/type: yes/0
Extra: 01d079bdc1079efc0ce411013f23f9c3a8c21af28756d5a78694237b7ef27e2b51021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fabd3e5b00ae59c0bc04a5e12435fb68b365c126d068918ffa1a5222ffa8214b 0.600000000000 1585624 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": 1107923, "vin": [ { "gen": { "height": 1107913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fabd3e5b00ae59c0bc04a5e12435fb68b365c126d068918ffa1a5222ffa8214b" } } ], "extra": [ 1, 208, 121, 189, 193, 7, 158, 252, 12, 228, 17, 1, 63, 35, 249, 195, 168, 194, 26, 242, 135, 86, 213, 167, 134, 148, 35, 123, 126, 242, 126, 43, 81, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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