Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 996d654380faafeef674ec72c6060e7c31911ead4cac46fbdd119ad11401792c

Tx prefix hash: 4b9b1773cea422d3001a138958acd37a638c482ba2adb1ec3bcc5be88b6a3f7c
Tx public key: 2cbdbe7f5cfc316ae2e3fa581d3c7ac0c5e34d5b7b59ecf8524711b76e5772c1
Timestamp: 1718289752 Timestamp [UCT]: 2024-06-13 14:42:32 Age [y:d:h:m:s]: 00:226:15:29:27
Block: 1043380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162145 RingCT/type: yes/0
Extra: 012cbdbe7f5cfc316ae2e3fa581d3c7ac0c5e34d5b7b59ecf8524711b76e5772c102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60b1a1f628f1d533d7d70b53ec4818b8af3589bd74ce4491a706b5b8e9d5fcbf 0.600000000000 1512521 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": 1043390, "vin": [ { "gen": { "height": 1043380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60b1a1f628f1d533d7d70b53ec4818b8af3589bd74ce4491a706b5b8e9d5fcbf" } } ], "extra": [ 1, 44, 189, 190, 127, 92, 252, 49, 106, 226, 227, 250, 88, 29, 60, 122, 192, 197, 227, 77, 91, 123, 89, 236, 248, 82, 71, 17, 183, 110, 87, 114, 193, 2, 17, 0, 0, 0, 2, 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