Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65ec5a59354f3301c4b5122b104f6219771fb92a1de6e49bbd5f4fcd061db216

Tx prefix hash: dc7a9c2e2d91f01a747213c9f7ebebfa958d4da7c0e1049fe4da2c661d6c419c
Tx public key: 6315d002f8e3720dad06420c49b4696929ae3e5640c17b82d525d3b690a3bc43
Timestamp: 1736903929 Timestamp [UCT]: 2025-01-15 01:18:49 Age [y:d:h:m:s]: 00:154:23:18:54
Block: 1197544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110464 RingCT/type: yes/0
Extra: 016315d002f8e3720dad06420c49b4696929ae3e5640c17b82d525d3b690a3bc430211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b36373d5d5fe99ed22697e49f095936f48eb6ffcf0182c3d0632427d943ebe39 0.600000000000 1684155 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": 1197554, "vin": [ { "gen": { "height": 1197544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b36373d5d5fe99ed22697e49f095936f48eb6ffcf0182c3d0632427d943ebe39" } } ], "extra": [ 1, 99, 21, 208, 2, 248, 227, 114, 13, 173, 6, 66, 12, 73, 180, 105, 105, 41, 174, 62, 86, 64, 193, 123, 130, 213, 37, 211, 182, 144, 163, 188, 67, 2, 17, 0, 0, 0, 2, 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