Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f4265eb1b7be0bd5fa1d6046587ea86cb1c5d2797266014f3a5e95818618fa1

Tx prefix hash: 957c303f2d7040c2b994ba2a14ca752d0940e21390ac99864693271348b4a36b
Tx public key: 500a62476fc8e993cb8328b8ae12b744699dd6f05050e397abae2147a414fd7b
Timestamp: 1712927023 Timestamp [UCT]: 2024-04-12 13:03:43 Age [y:d:h:m:s]: 00:226:06:21:09
Block: 998898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161994 RingCT/type: yes/0
Extra: 01500a62476fc8e993cb8328b8ae12b744699dd6f05050e397abae2147a414fd7b02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc162802cab0e8cb0942528ee0e668b7b1e82018611eeb5439313ce59321b3be 0.600000000000 1459370 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": 998908, "vin": [ { "gen": { "height": 998898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc162802cab0e8cb0942528ee0e668b7b1e82018611eeb5439313ce59321b3be" } } ], "extra": [ 1, 80, 10, 98, 71, 111, 200, 233, 147, 203, 131, 40, 184, 174, 18, 183, 68, 105, 157, 214, 240, 80, 80, 227, 151, 171, 174, 33, 71, 164, 20, 253, 123, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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