Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c074086fbdad5ea4652f90c6f48271a3024d7468041f4b88751ba76117eff71

Tx prefix hash: 5de828f8dde870bf7fbf791a08753d10e504fd5ee2a6e26d9f8fa917ca6f7e20
Tx public key: 667d3e120ff534baf2f29fb3e4303c5571f2e5dd391044adf0919df5ef71940a
Timestamp: 1626883247 Timestamp [UCT]: 2021-07-21 16:00:47 Age [y:d:h:m:s]: 03:196:01:45:31
Block: 298333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 911607 RingCT/type: yes/0
Extra: 01667d3e120ff534baf2f29fb3e4303c5571f2e5dd391044adf0919df5ef71940a02110000000967b8e4bc000000000000000000

1 output(s) for total of 63.023050434000 dcy

stealth address amount amount idx
00: 401be71a1f08dd406b23dcc12df47473df2e343ac8b0918961ad7413f095a73b 63.023050434000 624164 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": 298343, "vin": [ { "gen": { "height": 298333 } } ], "vout": [ { "amount": 63023050434, "target": { "key": "401be71a1f08dd406b23dcc12df47473df2e343ac8b0918961ad7413f095a73b" } } ], "extra": [ 1, 102, 125, 62, 18, 15, 245, 52, 186, 242, 242, 159, 179, 228, 48, 60, 85, 113, 242, 229, 221, 57, 16, 68, 173, 240, 145, 157, 245, 239, 113, 148, 10, 2, 17, 0, 0, 0, 9, 103, 184, 228, 188, 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