Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feb6f0cffbe0777b11ce65111650d905e172e443242a0094e52f67c101d2e44b

Tx prefix hash: 9182664edc6d0c2a453025215907f1c71f98dfe9d1b764303f4245f6bd1d80c2
Tx public key: 9aee7cf8b0a256f8222314adbc192cc469cad906830cbbf84441e6be7183e1cb
Timestamp: 1582185236 Timestamp [UCT]: 2020-02-20 07:53:56 Age [y:d:h:m:s]: 05:070:04:33:26
Block: 68604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1203409 RingCT/type: yes/0
Extra: 019aee7cf8b0a256f8222314adbc192cc469cad906830cbbf84441e6be7183e1cb02110000000cd81c26c0000000000000000000

1 output(s) for total of 363.653083870000 dcy

stealth address amount amount idx
00: 54a6b91cafcf549a6ed15f6c2e33ebd8640ea50955a23011f8e7ee0000c2b61f 363.653083870000 126485 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": 68614, "vin": [ { "gen": { "height": 68604 } } ], "vout": [ { "amount": 363653083870, "target": { "key": "54a6b91cafcf549a6ed15f6c2e33ebd8640ea50955a23011f8e7ee0000c2b61f" } } ], "extra": [ 1, 154, 238, 124, 248, 176, 162, 86, 248, 34, 35, 20, 173, 188, 25, 44, 196, 105, 202, 217, 6, 131, 12, 187, 248, 68, 65, 230, 190, 113, 131, 225, 203, 2, 17, 0, 0, 0, 12, 216, 28, 38, 192, 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