Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a60c9ad4bf16c9e3150121fb14d77b5f272827cba18a3d7a94711262303021b2

Tx prefix hash: fc2e380dc58d2c580efeaf48bb6144719540a5995e39a830edb45d921bc04a97
Tx public key: 550a2a9cb05d88d51728092da243560efc7fe7bbb0bcc58a43495f0efa05aaaa
Timestamp: 1681137599 Timestamp [UCT]: 2023-04-10 14:39:59 Age [y:d:h:m:s]: 02:214:01:15:45
Block: 735608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 672858 RingCT/type: yes/0
Extra: 01550a2a9cb05d88d51728092da243560efc7fe7bbb0bcc58a43495f0efa05aaaa02110000000133af99f4000000000000000000

1 output(s) for total of 2.241948101000 dcy

stealth address amount amount idx
00: 998d9c4c1676424be6fe1c32712f019d16c92a7f9eb613eb2958b8847be2cf7a 2.241948101000 1181953 of 0

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": 735618, "vin": [ { "gen": { "height": 735608 } } ], "vout": [ { "amount": 2241948101, "target": { "key": "998d9c4c1676424be6fe1c32712f019d16c92a7f9eb613eb2958b8847be2cf7a" } } ], "extra": [ 1, 85, 10, 42, 156, 176, 93, 136, 213, 23, 40, 9, 45, 162, 67, 86, 14, 252, 127, 231, 187, 176, 188, 197, 138, 67, 73, 95, 14, 250, 5, 170, 170, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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