Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 632b477b3011f747c4a635ce5fe28d5e878f4a579031f42276f2ec295e517ff4

Tx prefix hash: 2b134a02332da3a635cce216adcb296b9ed0bc2136b8670ce5d128eea14fc844
Tx public key: a94f6f2fd0c51b54f13748ef2c8aaef4b5ff0933df858165633cc6e42be9e9b0
Timestamp: 1735505130 Timestamp [UCT]: 2024-12-29 20:45:30 Age [y:d:h:m:s]: 00:098:17:12:41
Block: 1185964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70345 RingCT/type: yes/0
Extra: 01a94f6f2fd0c51b54f13748ef2c8aaef4b5ff0933df858165633cc6e42be9e9b00211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ebce3debabab978bede07d4204c7a1850d50057a217561a0d9688a60acd6f00 0.600000000000 1672439 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": 1185974, "vin": [ { "gen": { "height": 1185964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ebce3debabab978bede07d4204c7a1850d50057a217561a0d9688a60acd6f00" } } ], "extra": [ 1, 169, 79, 111, 47, 208, 197, 27, 84, 241, 55, 72, 239, 44, 138, 174, 244, 181, 255, 9, 51, 223, 133, 129, 101, 99, 60, 198, 228, 43, 233, 233, 176, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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