Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 568f59886464298bd8123817d3d0a780b0cb6cb813722b89bf60fd719f9984e1

Tx prefix hash: 3c908012c9890c274e32b62a2983b547918ca8325abd45479dfb98e28784f366
Tx public key: ca7d3c1f6e2f5a0c7948c3aa56debb01e29dc6790ef2136385e0fab8fe104689
Timestamp: 1732416156 Timestamp [UCT]: 2024-11-24 02:42:36 Age [y:d:h:m:s]: 00:145:13:49:45
Block: 1160400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103862 RingCT/type: yes/0
Extra: 01ca7d3c1f6e2f5a0c7948c3aa56debb01e29dc6790ef2136385e0fab8fe1046890211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d46f66842aa8fac5fe2d95c6355f3987d121fffae8cefd1fa43b740646998d5 0.600000000000 1646047 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": 1160410, "vin": [ { "gen": { "height": 1160400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d46f66842aa8fac5fe2d95c6355f3987d121fffae8cefd1fa43b740646998d5" } } ], "extra": [ 1, 202, 125, 60, 31, 110, 47, 90, 12, 121, 72, 195, 170, 86, 222, 187, 1, 226, 157, 198, 121, 14, 242, 19, 99, 133, 224, 250, 184, 254, 16, 70, 137, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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