Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 667800045dc4af7ed09b58a9d99269520df34f9b52130a11a303ff21f7dd2407

Tx prefix hash: bf7f748e1cc7cc9c414b2a021492172d9e1dd59cd0b1cced51ccb1fb19d89711
Tx public key: 7a334659829cf866652a9782ae5f11cbd47a9a2b4866ca5906b067af177b48dd
Timestamp: 1576085383 Timestamp [UCT]: 2019-12-11 17:29:43 Age [y:d:h:m:s]: 05:070:11:13:12
Block: 25473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196202 RingCT/type: yes/0
Extra: 017a334659829cf866652a9782ae5f11cbd47a9a2b4866ca5906b067af177b48dd021100000012d81c26c0000000000000000000

1 output(s) for total of 505.374383249000 dcy

stealth address amount amount idx
00: 4ed8c55b272d46d70b30e65bf931403e297a6cf9267392165438c96f22aab3d7 505.374383249000 41998 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": 25483, "vin": [ { "gen": { "height": 25473 } } ], "vout": [ { "amount": 505374383249, "target": { "key": "4ed8c55b272d46d70b30e65bf931403e297a6cf9267392165438c96f22aab3d7" } } ], "extra": [ 1, 122, 51, 70, 89, 130, 156, 248, 102, 101, 42, 151, 130, 174, 95, 17, 203, 212, 122, 154, 43, 72, 102, 202, 89, 6, 176, 103, 175, 23, 123, 72, 221, 2, 17, 0, 0, 0, 18, 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