Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33e5fe157de3626b142cb05610e0e8ce659b0ff3e666c1831e721037f794dedb

Tx prefix hash: fa3de38e4ab1d22c95d899391ec7f5d42a75eb77c5cefe0bbcc8ff1c8eb924e8
Tx public key: 27b3bfd644b32778bbfb4dd93a63aa53be8fd05c13f23c9bfc71cf1f57fee238
Timestamp: 1727497625 Timestamp [UCT]: 2024-09-28 04:27:05 Age [y:d:h:m:s]: 00:169:06:39:57
Block: 1119718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120794 RingCT/type: yes/0
Extra: 0127b3bfd644b32778bbfb4dd93a63aa53be8fd05c13f23c9bfc71cf1f57fee23802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1aa6db522b3a9e60fe18eb885923f5199163ae78469c9a3d47d123b62c05356e 0.600000000000 1601379 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": 1119728, "vin": [ { "gen": { "height": 1119718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1aa6db522b3a9e60fe18eb885923f5199163ae78469c9a3d47d123b62c05356e" } } ], "extra": [ 1, 39, 179, 191, 214, 68, 179, 39, 120, 187, 251, 77, 217, 58, 99, 170, 83, 190, 143, 208, 92, 19, 242, 60, 155, 252, 113, 207, 31, 87, 254, 226, 56, 2, 17, 0, 0, 0, 2, 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