Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b04b86ba916ae8bef7cc7e4a6b99725b35f088da72ff630c2d1b56419931c74

Tx prefix hash: 6351bbeb58d33c946e65f8a9b1c8f726e767d793ff40898e63cfd1ea900921ed
Tx public key: ff8f57e7af9011c1bc15c8700c2bd321d1ac089eeaba6efcc090ae1691f23014
Timestamp: 1726231409 Timestamp [UCT]: 2024-09-13 12:43:29 Age [y:d:h:m:s]: 00:274:06:07:02
Block: 1109214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195804 RingCT/type: yes/0
Extra: 01ff8f57e7af9011c1bc15c8700c2bd321d1ac089eeaba6efcc090ae1691f23014021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9599c9e3b58faddf212e03f1cb4867cab0b164ae3dae9f4525ce138aac4fd97 0.600000000000 1587383 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": 1109224, "vin": [ { "gen": { "height": 1109214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9599c9e3b58faddf212e03f1cb4867cab0b164ae3dae9f4525ce138aac4fd97" } } ], "extra": [ 1, 255, 143, 87, 231, 175, 144, 17, 193, 188, 21, 200, 112, 12, 43, 211, 33, 209, 172, 8, 158, 234, 186, 110, 252, 192, 144, 174, 22, 145, 242, 48, 20, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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