Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0a3e24a1f6bf56983937cfe786106bca528b773a9ad09d167a2c91e8db6259c

Tx prefix hash: 3279f07914c96e7d8e0e3c8fc0064e7e5485b1b298c097fa14d1ed21d86b8ecd
Tx public key: f62c06dbf27c22bef82689411f646dbf6b94df1ac05e90ae0b0f511d859fd5ac
Timestamp: 1725328471 Timestamp [UCT]: 2024-09-03 01:54:31 Age [y:d:h:m:s]: 00:209:15:19:09
Block: 1101731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149670 RingCT/type: yes/0
Extra: 01f62c06dbf27c22bef82689411f646dbf6b94df1ac05e90ae0b0f511d859fd5ac021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f95b2b87d78ed8a88e497a2080e42495a70cdece1f892cb2e05942168aa7892 0.600000000000 1577894 of 15

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": 1101741, "vin": [ { "gen": { "height": 1101731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f95b2b87d78ed8a88e497a2080e42495a70cdece1f892cb2e05942168aa7892" } } ], "extra": [ 1, 246, 44, 6, 219, 242, 124, 34, 190, 248, 38, 137, 65, 31, 100, 109, 191, 107, 148, 223, 26, 192, 94, 144, 174, 11, 15, 81, 29, 133, 159, 213, 172, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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