Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b05f6fdbb60e81074a0a1a5591431caed5a447a4aaddc8d35de8c3529072a50f

Tx prefix hash: e2e334c42f9f816ca8b6e7b945676c395eaeded016e806172cba982218af3971
Tx public key: f57b4864a9d21d768ba957446b3e656c04ff6e3ddb809d7ff2fa22f92281463c
Timestamp: 1709685089 Timestamp [UCT]: 2024-03-06 00:31:29 Age [y:d:h:m:s]: 01:038:08:54:22
Block: 972048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288423 RingCT/type: yes/0
Extra: 01f57b4864a9d21d768ba957446b3e656c04ff6e3ddb809d7ff2fa22f92281463c02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f91c0e9467d6c3c84358f8871f6653c55b231e86bf9ccef19c96bdabc683237b 0.600000000000 1431953 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": 972058, "vin": [ { "gen": { "height": 972048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f91c0e9467d6c3c84358f8871f6653c55b231e86bf9ccef19c96bdabc683237b" } } ], "extra": [ 1, 245, 123, 72, 100, 169, 210, 29, 118, 139, 169, 87, 68, 107, 62, 101, 108, 4, 255, 110, 61, 219, 128, 157, 127, 242, 250, 34, 249, 34, 129, 70, 60, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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