Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6103198ee0e32f1f51e9131e6ce44e41e708d8f3e6abb431ee5da23c0d94cd3a

Tx prefix hash: 0db141111c6fc11b7f7a8d53cc745a7983d4b212381c29b4931ac7a6403c90ca
Tx public key: 6d8defdf02d79a69f2dde7a2cc11eca4902da4d19f7094ac825e07984e427366
Timestamp: 1732778954 Timestamp [UCT]: 2024-11-28 07:29:14 Age [y:d:h:m:s]: 00:131:04:05:42
Block: 1163402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93550 RingCT/type: yes/0
Extra: 016d8defdf02d79a69f2dde7a2cc11eca4902da4d19f7094ac825e07984e4273660211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b19daaffaa5aa6eae4922128a82434ce0f248d361ec034a855a003cda1a36f8d 0.600000000000 1649069 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": 1163412, "vin": [ { "gen": { "height": 1163402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b19daaffaa5aa6eae4922128a82434ce0f248d361ec034a855a003cda1a36f8d" } } ], "extra": [ 1, 109, 141, 239, 223, 2, 215, 154, 105, 242, 221, 231, 162, 204, 17, 236, 164, 144, 45, 164, 209, 159, 112, 148, 172, 130, 94, 7, 152, 78, 66, 115, 102, 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