Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81c54f4222498caf24089425181e444bb98958939d09e17d2e762c8880d0a10b

Tx prefix hash: 7da1e53926a3b495eb2a7f33aa1c8352ea979ba04efd42c42f908b08d6968602
Tx public key: 8aa04d5ef159ce22257df11ec695a08e0e9ad589eef7e4f364bf499cf7f1a9fd
Timestamp: 1727499532 Timestamp [UCT]: 2024-09-28 04:58:52 Age [y:d:h:m:s]: 01:041:07:58:06
Block: 1119730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287932 RingCT/type: yes/0
Extra: 018aa04d5ef159ce22257df11ec695a08e0e9ad589eef7e4f364bf499cf7f1a9fd02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cfdae87d39cf42de7bc83be473dc2da289e091e32946e04ec7ca8071e8fb481 0.600000000000 1601395 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": 1119740, "vin": [ { "gen": { "height": 1119730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cfdae87d39cf42de7bc83be473dc2da289e091e32946e04ec7ca8071e8fb481" } } ], "extra": [ 1, 138, 160, 77, 94, 241, 89, 206, 34, 37, 125, 241, 30, 198, 149, 160, 142, 14, 154, 213, 137, 238, 247, 228, 243, 100, 191, 73, 156, 247, 241, 169, 253, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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