Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36a0759cd0b517210e526eed1231a14d2c1fcc613e60226617ba14452074db70

Tx prefix hash: 1112badd656f7d07973d97c3937abf3e6b15384d7b9d8c371474bb1a6a2a51d6
Tx public key: fd9fe5e8d2965d1913eb4cb8fef1498dc9f35bf17c38a6f4373b861b692df2d3
Timestamp: 1696403022 Timestamp [UCT]: 2023-10-04 07:03:42 Age [y:d:h:m:s]: 01:186:13:12:03
Block: 862125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394364 RingCT/type: yes/0
Extra: 01fd9fe5e8d2965d1913eb4cb8fef1498dc9f35bf17c38a6f4373b861b692df2d30211000000014b8f5122000000000000000000

1 output(s) for total of 0.853929523000 dcy

stealth address amount amount idx
00: a35e2787744a69fcf1fa5711524b77e31fa8fd0c05e245d5eac9d20725f93a22 0.853929523000 1316513 of 0

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": 862135, "vin": [ { "gen": { "height": 862125 } } ], "vout": [ { "amount": 853929523, "target": { "key": "a35e2787744a69fcf1fa5711524b77e31fa8fd0c05e245d5eac9d20725f93a22" } } ], "extra": [ 1, 253, 159, 229, 232, 210, 150, 93, 25, 19, 235, 76, 184, 254, 241, 73, 141, 201, 243, 91, 241, 124, 56, 166, 244, 55, 59, 134, 27, 105, 45, 242, 211, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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