Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 898824ecc0b08559953027b2ef1134de1e406d43776be5c8b2af1aeccc76e4c5

Tx prefix hash: 77823b85fdfffddf5cd07d513c24d57d4d7c9a9ab7f4323c47bfb330df2ff1b4
Tx public key: a4443a61783b82db82efa93a2ea983f31266eb16656c5b582158e1738c45fa0a
Timestamp: 1710599507 Timestamp [UCT]: 2024-03-16 14:31:47 Age [y:d:h:m:s]: 01:020:18:38:47
Block: 979640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275812 RingCT/type: yes/0
Extra: 01a4443a61783b82db82efa93a2ea983f31266eb16656c5b582158e1738c45fa0a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 055b82cfce3a4dde3324342b5e334d0b2731fc2db51828303d696158d0ec8220 0.600000000000 1439683 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": 979650, "vin": [ { "gen": { "height": 979640 } } ], "vout": [ { "amount": 600000000, "target": { "key": "055b82cfce3a4dde3324342b5e334d0b2731fc2db51828303d696158d0ec8220" } } ], "extra": [ 1, 164, 68, 58, 97, 120, 59, 130, 219, 130, 239, 169, 58, 46, 169, 131, 243, 18, 102, 235, 22, 101, 108, 91, 88, 33, 88, 225, 115, 140, 69, 250, 10, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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