Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91e2533c7d67915ae0e9a9388874daec9e806ca6000f3ec78b3b516b8195ae9e

Tx prefix hash: 7f2fa04a75cf6d6d4b9c62e92f3fe0cf5ce3d78566d0ff78898c90580c006d1f
Tx public key: 463d183e221da65eae0027a9f80fcd0361d5ac5220b3f303a5d8c2757efd5556
Timestamp: 1578847981 Timestamp [UCT]: 2020-01-12 16:53:01 Age [y:d:h:m:s]: 05:297:14:53:48
Block: 44104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1360544 RingCT/type: yes/0
Extra: 01463d183e221da65eae0027a9f80fcd0361d5ac5220b3f303a5d8c2757efd55560211000000134943cd9f000000000000000000

1 output(s) for total of 438.395392580000 dcy

stealth address amount amount idx
00: ac6b24ffe9dd2d6bc331219346c6f40f9f66e4c03f5670083602383e36cecb70 438.395392580000 80156 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": 44114, "vin": [ { "gen": { "height": 44104 } } ], "vout": [ { "amount": 438395392580, "target": { "key": "ac6b24ffe9dd2d6bc331219346c6f40f9f66e4c03f5670083602383e36cecb70" } } ], "extra": [ 1, 70, 61, 24, 62, 34, 29, 166, 94, 174, 0, 39, 169, 248, 15, 205, 3, 97, 213, 172, 82, 32, 179, 243, 3, 165, 216, 194, 117, 126, 253, 85, 86, 2, 17, 0, 0, 0, 19, 73, 67, 205, 159, 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