Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3c3803157b6708205e62e1e86f49b2257e54d7e419c1a34985348f76de685e3

Tx prefix hash: 6968a23ff11f0ef091159700c697ebf6e668253b07d1388e4932fe23e1af233f
Tx public key: b510e9cfb03cc3eeef1468d88436c501c3aaee8d425c63a517c5a91fc8867df7
Timestamp: 1729411089 Timestamp [UCT]: 2024-10-20 07:58:09 Age [y:d:h:m:s]: 00:217:03:40:17
Block: 1135567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155019 RingCT/type: yes/0
Extra: 01b510e9cfb03cc3eeef1468d88436c501c3aaee8d425c63a517c5a91fc8867df7021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eeae4ac50eaac83633cead326d3f8c0526eb7d061d68e7aadba6b00c991040f4 0.600000000000 1618906 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": 1135577, "vin": [ { "gen": { "height": 1135567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eeae4ac50eaac83633cead326d3f8c0526eb7d061d68e7aadba6b00c991040f4" } } ], "extra": [ 1, 181, 16, 233, 207, 176, 60, 195, 238, 239, 20, 104, 216, 132, 54, 197, 1, 195, 170, 238, 141, 66, 92, 99, 165, 23, 197, 169, 31, 200, 134, 125, 247, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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