Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e980c49e989969b797b16d1d289a0264134a6dc25ac87e190211d9f3dfccdfa6

Tx prefix hash: 71c062b6c7626b50c5528d93e4c41af87c4a83d4787b60d7817450e186c4433e
Tx public key: 440a372d01cd4de53f02c57805d354159c6dce1ecfe4fd893ecd1fa17e40d6c3
Timestamp: 1628823705 Timestamp [UCT]: 2021-08-13 03:01:45 Age [y:d:h:m:s]: 03:146:17:50:29
Block: 312882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 878116 RingCT/type: yes/0
Extra: 01440a372d01cd4de53f02c57805d354159c6dce1ecfe4fd893ecd1fa17e40d6c302110000002201f1e57f000000000000000000

1 output(s) for total of 56.401742584000 dcy

stealth address amount amount idx
00: c1b9a2f3c712dbab4c02b67500d86e327ccdc13f37befe1b85ad9e62460c7e8c 56.401742584000 650991 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": 312892, "vin": [ { "gen": { "height": 312882 } } ], "vout": [ { "amount": 56401742584, "target": { "key": "c1b9a2f3c712dbab4c02b67500d86e327ccdc13f37befe1b85ad9e62460c7e8c" } } ], "extra": [ 1, 68, 10, 55, 45, 1, 205, 77, 229, 63, 2, 197, 120, 5, 211, 84, 21, 156, 109, 206, 30, 207, 228, 253, 137, 62, 205, 31, 161, 126, 64, 214, 195, 2, 17, 0, 0, 0, 34, 1, 241, 229, 127, 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