Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a770c2029c33769d9ced64b3f8d9dbeab207231e5ce8ded3817420fd31d43bf

Tx prefix hash: 9e171c6ea81234be74855c2488c9b65667b35acf7b8651ab8cd131974169930c
Tx public key: 44d70d8b83a197ec1cfa45d3c58ca8bc23a60aab5aefaf50c9b41e5b1b679f9f
Timestamp: 1711826067 Timestamp [UCT]: 2024-03-30 19:14:27 Age [y:d:h:m:s]: 01:012:05:12:18
Block: 989809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269681 RingCT/type: yes/0
Extra: 0144d70d8b83a197ec1cfa45d3c58ca8bc23a60aab5aefaf50c9b41e5b1b679f9f0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71f8d2d57dc93188ac97d50afa2f08d0a770b44228c279ad01d67dae52eed820 0.600000000000 1450127 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": 989819, "vin": [ { "gen": { "height": 989809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71f8d2d57dc93188ac97d50afa2f08d0a770b44228c279ad01d67dae52eed820" } } ], "extra": [ 1, 68, 215, 13, 139, 131, 161, 151, 236, 28, 250, 69, 211, 197, 140, 168, 188, 35, 166, 10, 171, 90, 239, 175, 80, 201, 180, 30, 91, 27, 103, 159, 159, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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