Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0274ce4578aef3c660688d0eaa9a24721a3cbb59999f1595d1b96b48b7f5279c

Tx prefix hash: 4cedeb1282ad327cb14e31e3f01ffedeb3f85eaa58c9ef732c6a0299c6b400ca
Tx public key: 1362d8849c3b15ab658ea61ec76b9220fe2c7f2a0904a5f10c6edbd1852df130
Timestamp: 1736728393 Timestamp [UCT]: 2025-01-13 00:33:13 Age [y:d:h:m:s]: 00:338:14:19:36
Block: 1196091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239551 RingCT/type: yes/0
Extra: 011362d8849c3b15ab658ea61ec76b9220fe2c7f2a0904a5f10c6edbd1852df1300211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1320db667d077a266caab3f581d671f539a4553b5458ea3e6dd3b1ee008f60ab 0.600000000000 1682688 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": 1196101, "vin": [ { "gen": { "height": 1196091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1320db667d077a266caab3f581d671f539a4553b5458ea3e6dd3b1ee008f60ab" } } ], "extra": [ 1, 19, 98, 216, 132, 156, 59, 21, 171, 101, 142, 166, 30, 199, 107, 146, 32, 254, 44, 127, 42, 9, 4, 165, 241, 12, 110, 219, 209, 133, 45, 241, 48, 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