Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ece9e3af7c54b3a5bddb7c5fbf66e5df1f396b27c677c8ba4b784c46005444b

Tx prefix hash: 2c6cf67896168a43287e2e51f2b260e2bcb8ced302cf200a92be3cbb287e56d0
Tx public key: 8d6bf2d526d614f39f75ca4224ea0a13533f6d5b7ca345e3399096ee51371bad
Timestamp: 1735471889 Timestamp [UCT]: 2024-12-29 11:31:29 Age [y:d:h:m:s]: 00:353:00:01:10
Block: 1185691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249846 RingCT/type: yes/0
Extra: 018d6bf2d526d614f39f75ca4224ea0a13533f6d5b7ca345e3399096ee51371bad021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b27e0f08456337c58465959151bdc91ab6cf935b7126a71619ef0d6adcd7770 0.600000000000 1672166 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": 1185701, "vin": [ { "gen": { "height": 1185691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b27e0f08456337c58465959151bdc91ab6cf935b7126a71619ef0d6adcd7770" } } ], "extra": [ 1, 141, 107, 242, 213, 38, 214, 20, 243, 159, 117, 202, 66, 36, 234, 10, 19, 83, 63, 109, 91, 124, 163, 69, 227, 57, 144, 150, 238, 81, 55, 27, 173, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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